02. Getting Started

Introduction

In this section we're going to walk through the starter code that will form the foundation of our project. In the next few lessons we will walk through all the steps of setting up webpack on this node and express app.

FEND C04 L02 A02 Getting Started

Getting Set Up

This course is going to include a lot of work on your own repository. We chose this style of course work for many reasons, the main reason being that no one memorizes these configuration settings. In fact it is probably not to your benefit to do so. By the end of the course, we want you to own a solid example to look back at for new projects. Also, when working on your own repository you have more freedom to try things and change things - which is an excellent way to learn! Just remember to stop and make a branch or at least commit before going off onto a rabbit trail.

Right now, take some time to just get this starter code up and running on your machine before we start with Webpack. You’ll have two options here: 1) Fork this repo then clone it onto your own machine, or 2) you can use the in-classroom workspaces spread throughout this lesson, so that you don’t need to deal with any environment setup. Can you remember the steps for getting a project like this set up? Don’t worry, you can always take a look at the project readme if you have any trouble. You are good to go when you can see the page we saw in the demo.

This repository is going to be an important resource for you throughout this course, take a minute to poke around. Each section of our webpack setup is reflected as its own branch in the repository, and each branch has a file documenting the steps taken in the branch. When you fork the repo, you can add your own personal notes to this markdown file.

Quiz

When you use npm to install a new package, how many files/folders in your code change?

SOLUTION: 3

Quiz

What do the commands npm i or yarn do? Choose the best answer.

SOLUTION: They install all modules listed in the package.json and add to or create a new node_modules folder

FEND C04 L2 Question 2

Interview Question

QUESTION:

Interview Question

What information can go into a package.json file? Name everything you can think of.

ANSWER:

Things that must be in your answer:
Npm scripts
Dependencies (should mention dev dependencies vs general dependencies)
App information (name, version, license, etc..)
Potential answers for this question:
Github repo name
Starting point
NPM privacy

… if you want to take a look at all the things, go here: https://docs.npmjs.com/files/package.json